fix(skill): add merge conflict check in pull-request convergence loop - #3237
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughUpdated the pull-request skill's convergence loop to add an early mergeable status check (step 2b) that stops iteration if a merge conflict is detected, instead of only checking at the final stop condition. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related issues
Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
This PR updates the /pull-request skill’s convergence loop to detect merge conflicts earlier, so the loop stops immediately when a PR becomes unmergeable mid-iteration (as requested in #3236).
Changes:
- Add a mid-loop
mergeablestatus check (step 2b) after CI passes. - Stop early and report to the user if the PR is
CONFLICTING. - Update the stop-condition section (6f) to reference the new step 2b check.
…icit UNKNOWN handling
Summary
Closes #3236
Test plan
Summary by CodeRabbit